Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(bridge-ui): fix issue where balance is shown for wrong token #16541

Merged
merged 4 commits into from
Mar 30, 2024
Merged

fix(bridge-ui): fix issue where balance is shown for wrong token #16541

merged 4 commits into from
Mar 30, 2024

Conversation

SihanoukSolver29
Copy link
Contributor

Summary

When I was testing the testnet with the HORSE ERC20 token, trying to bridge it, at the "Review" stage of the bridging process I pressed edit and it went back to the first "Import" stage. At that point I saw "Balance: 50 HORSE" and thought the HORSE token was still selected, so I entered 1 for the amount and bridged but, unbeknown to me, ETH was actually selected instead and it transferred ETH instead of HORSE. Since I can see this being a problem for users in the future I've fixed the issue by making sure the Balance shown is of the selected ETH.

STEPS TO REPRODUCE

1 ) Select the HORSE token for bridging
1

2 ) Go back to the first "Import" stage by either presing 'Edit' or 'Go Back'
2

3 ) Observe that ETH is selected as the default coin but the HORSE balance is shown
3

@dantaik dantaik added this pull request to the merge queue Mar 30, 2024
Merged via the queue into taikoxyz:main with commit 1dd47cf Mar 30, 2024
4 checks passed
Copy link

gitpoap-bot bot commented Mar 30, 2024

Congrats, your important contribution to this open-source project has earned you a GitPOAP!

GitPOAP: 2024 Taiko Contributor:

GitPOAP: 2024 Taiko Contributor GitPOAP Badge

Head to gitpoap.io & connect your GitHub account to mint!

Learn more about GitPOAPs here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants